Problem

When running evaluations with suspend/resume, two separate entries are created in StudioWeb instead of updating the same entry:

Entry #1 (Suspend Phase):

• Status: "suspended"
• Contains: Triggers for resume
• Missing: Evaluator results

Entry #2 (Resume Phase):

• Status: "completed"
• Contains: Evaluator results
• Missing: Suspend information

Both entries have the same evalSetRunId and evalSnapshot.id but different entry IDs, causing confusion in the SW UI.

Root Cause

The CREATE_EVAL_RUN event is published on BOTH suspend execution AND resume execution in src/uipath/_cli/_evals/_runtime.py (lines 516-522).

Execution Flow

Suspend Phase:

1. Line 516: Publishes CREATE_EVAL_RUN → Creates Entry Feat/basic invoke process #1
2. Agent executes and calls interrupt() → Returns SUSPENDED
3. Line 610: Publishes UPDATE_EVAL_RUN → Updates Entry Feat/basic invoke process #1 with suspend info

Resume Phase:

1. Line 516: Publishes CREATE_EVAL_RUN AGAIN → Creates Entry Refactor/folder layout #2 ❌
2. Agent resumes and completes execution
3. Line 610+: Publishes UPDATE_EVAL_RUN → Updates Entry Refactor/folder layout #2 with completion info

Solution

Added a check for self.context.resume before publishing CREATE_EVAL_RUN:

# Only create eval run entry if NOT resuming from a checkpoint
# When resuming, the entry already exists from the suspend phase
if not self.context.resume:
    await self.event_bus.publish(
        EvaluationEvents.CREATE_EVAL_RUN,
        EvalRunCreatedEvent(
            execution_id=execution_id,
            eval_item=eval_item,
        ),
    )

Now:

• On initial execution: Creates new eval run entry (as before)
• On resume: Skips creation, only updates the existing entry

Impact

✅ Users will see a single eval run entry with complete lifecycle:
pending → suspended → completed

✅ StudioWeb UI will show cleaner results and accurate metrics

✅ Trace data will have a single eval run with complete history

Testing

Tested with local suspend/resume evaluation cycles to verify:

• Only ONE entry is created in SW
• Entry is updated correctly during suspend phase
• Entry is updated correctly during resume phase
• No duplicate entries appear

Related Documentation

Investigation documented in: SUSPEND_RESUME_DUPLICATE_ENTRIES_INVESTIGATION.md (backend repo)